home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000824-20010305
/
000258_news@columbia.edu _Tue Feb 6 17:00:46 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2001-03-05
|
2KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA02884
for <kermit.misc@cpunix.cc.columbia.edu>; Tue, 6 Feb 2001 17:00:39 -0500 (EST)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA29472
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 6 Feb 2001 16:45:12 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id QAA29953
for kermit.misc@watsun.cc.columbia.edu; Tue, 6 Feb 2001 16:34:33 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: Unrecognized com port
Message-ID: <R5CBsHEH2Pqt@cc.usu.edu>
Date: 6 Feb 01 14:04:18 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
In article <fvWf6.2909$IK6.47145@news6.giganews.com>, "Steve" <steve@baus-systems.com> writes:
> Is there a list of reasons why I would get an unrecognized hardware when
> trying to use a com port from time to time? I am using 3.15 with Win98 2nd
> Edition on a PC in my office and never have a problem yet a remote location
> has the exact same OS and same com drivers and they have all sorts of com
> issues. I can not see any reason why as I have gone through the Using MSK
> in 32 bit Windows list of issues and do not see anything that applies. I
> would have thought booting the PC to DOS would be one way around this but
> that always gives errors.
>
> Any help would be greatly appreciated,
> Steve
---------
In a nut shell, Windows owns the hardware and may present a virtualized
version of parts, if it feels generous that day. Competition for say a serial
port means trouble.
Please keep in mind folks have a habit of both installing additional
software, configuring new things, and adjusting the basic machine (Bios etc)
so "same" does not apply to a particular machine from one week to the next.
Booting to DOS is trivial. Edit msdos.sys and have line BootGUI=0
present. Type win to start the GUI when you are ready. I operate this way
all the time (such as right now, using MSK to deal with email/etc).
Joe D.